Decoded claims are untrusted until verified
Anyone can construct a token-shaped string with arbitrary header and payload values. Reading sub, role, exp, or other claims tells you what the token says; it does not prove who issued it.
Decode JWT Header/Payload, exp·iat·nbf, and key claims, and verify the HS256 signature Browser only.
{}
{}
JWT payloads are usually just Base64URL-encoded claims and can be decoded without a key. That makes decoding useful for inspection but not for trust. Trust requires verifying the signature with the expected algorithm and key, then separately enforcing claims such as issuer, audience, and expiration.
Anyone can construct a token-shaped string with arbitrary header and payload values. Reading sub, role, exp, or other claims tells you what the token says; it does not prove who issued it.
This tool can verify HS256 signatures when you provide the matching secret. A successful signature check proves integrity under that shared key, but you still need application rules for expiration, issuer, audience, nonce, and other claims.
RS256 and ES256 use asymmetric keys and are not verified by this HS256-only checker. Do not interpret an unsupported algorithm as a failed or successful verification; use a verifier designed for that algorithm and key type.